Redis Cloud API MCP Server

Created By
Redisa year ago
Manage your Redis Cloud resources effortlessly using natural language. Create databases, monitor subscriptions, and configure cloud deployments with simple commands. Streamline your Redis Cloud experience and enhance productivity with intuitive interactions.
Overview

What is Redis Cloud API MCP Server?

Redis Cloud API MCP Server is a tool that allows users to manage their Redis Cloud resources effortlessly using natural language commands. It simplifies the process of creating databases, monitoring subscriptions, and configuring cloud deployments.

How to use Redis Cloud API MCP Server?

To use the Redis Cloud API MCP Server, you can interact with it through a compatible MCP Client, such as Claude Desktop, by issuing natural language commands like:

  • "Create a new Redis database in AWS"
  • "What are my current subscriptions?"
  • "Help me choose the right Redis database for my e-commerce application"

Key features of Redis Cloud API MCP Server?

  • Account Management: Retrieve details about your current Redis Cloud account and payment methods.
  • Subscription Management: Create and manage Pro and Essential subscriptions with advanced configuration options.
  • Database Capabilities: Access and manage available database modules and features.
  • Cloud Provider Management: Get information about available regions across cloud providers like AWS and GCP.
  • Task Management: Track and monitor tasks related to your Redis Cloud account.

Use cases of Redis Cloud API MCP Server?

  1. Creating and managing Redis databases in various cloud environments.
  2. Monitoring and configuring subscriptions for optimal resource usage.
  3. Assisting e-commerce applications in selecting the right database configurations.

FAQ from Redis Cloud API MCP Server?

  • Can I manage multiple cloud providers with this tool?

Yes! The Redis Cloud API MCP Server supports multi-cloud deployments across AWS, GCP, and Azure.

  • Is there a limit to the number of databases I can create?

The limits depend on your subscription plan; please refer to the plans and pricing section for details.

  • How do I authenticate my requests?

You need to provide your Redis Cloud API key and secret key in the server configuration.

Server Config

{
  "mcpServers": {
    "mcp-redis-cloud": {
      "command": "node",
      "args": [
        "--experimental-fetch",
        "<absolute_path_to_project_root>/dist/index.js"
      ],
      "env": {
        "API_KEY": "<redis_cloud_api_key>",
        "SECRET_KEY": "<redis_cloud_api_secret_key>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Redis
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago